@Rohith Hi. To have cmake to work for your project in this case , just unset the command CMAKE_PROJECT_INCLUDE_BEFORE and try again.
For visual studio Kit, just install microsoft visual studio 2019 build tools.
Hope it helps

@rahmanih said in Can't build QT6 on Windows using MingWin54:

Git BASH to run the build command.

You must not have any MSYS related stuff in your PATH - otherwise the build tools might pick them up (due to same name) and it will fail. You can see the problem already in your first output if I'm correct: "@C:/temp/qt6_min/qtbase/src/3rdparty/libjpeg/JpegPrivate_syncqt_args" - the forward slashes (but I might be wrong)

Attempt # 10 for building on windows [SUCCESS!!]

Started from scratch by re-downloading the source and used the subst command to make a new path to build with.

Created a virtual drive to avoid the PATH length limit: subst a: .\qt-everywhere-src-6.6.2\ created the build folder and ran the configure.bat like the following: PS a:\build> ..\configure.bat

Ran the command cmake --build . --parallel

Ran the install command afterwards

PS a:\build> cmake --build . --parallel

No issues and everything was installed.

Use Dependency Walker or it's successor Dependencies to find out what dlls the Qt mysql plugin needs. Most likely it's libmysql.dll and it's dependent dlls (openssl libs)

@Txai said in Possible virus threat on \Qt\6.5.0\mingw_64\bin \Qt63DRender.debug:

Suggestion?

Report to your antivirus tool and/or update your signatures. Don't know what Qt can do against a false positive.

@Christian-Ehrlicher What do you mean really make sure?

I call it inside the constructor of classes of my static libraries (if the class uses resources).

In my GUI application I call it in main after the application class (QApplication in this case) is created and before the main window is created.

@JonB sweet Jesus on the bike... this is the dumbest typo I ever made.

I am so embarrassed atm.

Thank you :D

@JoeCFD No, I refuse to. I tried once, perfectly healthy code that I maintained for 3 years on MingW didn't even want to compile (it was Qt only, no external libs), I refused to waste my time on Microsoft shenanigans.

Anyway, I got it to work. I was missing one thing in MinGW. For the record:

to use WinAPI with MinGW (I do it via Msys2) two packages are needed (I was missing the latter): msys2-w32api-headers and msys2-w32api-runtime. .pro file in the end looks like I was expecting: LIBS += -LC:/msys64/usr/lib/w32api/ -liphlpapi LIBS += -LC:/msys64/usr/lib/w32api/ -lws2_32 INCLUDEPATH += C:/msys64/usr/include/w32api DEPENDPATH += C:/msys64/usr/lib/w32api

Thank you everyone who contributed, thanks to your input I was able to trace and find my error. As always, your help is much appreciated.

after contact the qt support, they suggest me to replace

win32: LIBS += -L$$PWD/../../TinyLib/build-TinyLib-Qt_5_15_0_WebAssembly-Debug/ -lTinyLib

with

wasm:LIBS += -L$$PWD/../../TinyLib/build-TinyLib-Qt_5_15_0_WebAssembly-Debug/ -lTinyLib

For those experiencing the same problem as myself, check your path for perivous GNU mingw installation.
I personally am a GNU user, so i have 64-bit mingw installed on my desktop, that's causes a confliction with the one come with QT creator installation.